Skip to content

feat: Range Partitioning FFI#23520

Open
saadtajwar wants to merge 3 commits into
apache:mainfrom
saadtajwar:saadtajwar/range-partitioning-ffi
Open

feat: Range Partitioning FFI#23520
saadtajwar wants to merge 3 commits into
apache:mainfrom
saadtajwar:saadtajwar/range-partitioning-ffi

Conversation

@saadtajwar

@saadtajwar saadtajwar commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

Exposing range partition metadata via the FFI for external consumers

What changes are included in this PR?

  • Added FFI mirror struct for RangePartitioning and added new enum variant for range in FFI_Partitioning
  • For native -> FFI, added match arm for the new variant, same with FFI -> native but changed the approach of From -> TryFrom to utilize the validation for RangePartitioning and modified plan_properties to match
  • Added tests

Are these changes tested?

Yes

Are there any user-facing changes?

Yes, exposing Range partitioning over FFI. This exposes a new Range variant in the FFI_Partitioning enum, which may cause consumers of this enum to add another arm to match statements to handle the new enum. New FFI_RangePartitioning struct for the Range variant.

@github-actions github-actions Bot added the ffi Changes to the ffi crate label Jul 12, 2026
@saadtajwar

Copy link
Copy Markdown
Contributor Author

cc @gene-bordegaray ! Thanks again for all of the help reviewing! 😁 🥳

@saadtajwar saadtajwar force-pushed the saadtajwar/range-partitioning-ffi branch from e7eb901 to 4d95615 Compare July 12, 2026 18:21
@github-actions github-actions Bot added physical-expr Changes to the physical-expr crates proto Related to proto crate labels Jul 12, 2026
@saadtajwar saadtajwar force-pushed the saadtajwar/range-partitioning-ffi branch from 4d95615 to 89dd04e Compare July 12, 2026 18:23
@github-actions github-actions Bot removed physical-expr Changes to the physical-expr crates proto Related to proto crate labels Jul 12, 2026
@saadtajwar

Copy link
Copy Markdown
Contributor Author

cc @timsaucer :)

@timsaucer timsaucer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an API change since we're changing the signature. Can you please add a short note in the migration guide?

@timsaucer timsaucer added the api change Changes the API exposed to users of the crate label Jul 14, 2026
@timsaucer

Copy link
Copy Markdown
Member

Aside from the api change comment, looks good.

@saadtajwar

Copy link
Copy Markdown
Contributor Author

Thank you @timsaucer - just updated the description regarding the API change!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api change Changes the API exposed to users of the crate ffi Changes to the ffi crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose Range Partitioning Across FFI Boundaries

2 participants